-
Notifications
You must be signed in to change notification settings - Fork 213
chore: add Local Test Runner support for E2E Tests for RHDH core. #4023
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
chore: add Local Test Runner support for E2E Tests for RHDH core. #4023
Conversation
|
The image is available at: /test e2e-ocp-helm |
|
The image is available at: /test e2e-ocp-helm |
|
The image is available at: /test e2e-ocp-helm |
|
@subhashkhileri can you please fix the new sonar issues https://sonarcloud.io/project/issues?id=redhat-developer_rhdh&pullRequest=4023&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true |
8374063 to
9884207
Compare
9884207 to
810cad6
Compare
|
The image is available at: /test e2e-ocp-helm |
|
/review |
PR Reviewer Guide 🔍(Review updated until commit 82835ea)Here are some key observations to aid the review process:
|
Instead of hardcoding nodejs:18-ubi8, query the cluster for available nodejs imagestream tags and select the latest UBI9 version. Falls back to 18-ubi8 if no UBI9 tags are found. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
🚫 Image Push Skipped. The container image push was skipped because the build was skipped (either due to [skip-build] tag or no relevant changes with existing image) |
zdrapela
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No strong opinions here, but I have some thoughts on this 🤔
But great work overall!
| 2) JOB_NAME="periodic-ci-ocp-helm-nightly" ;; | ||
| 3) JOB_NAME="periodic-ci-ocp-operator-nightly" ;; | ||
| 4) JOB_NAME="periodic-ci-ocp-helm-upgrade-nightly" ;; | ||
| 5) JOB_NAME="periodic-ci-ocp-operator-auth-providers-nightly" ;; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: It won't have an effect, but we can align the job names with what's really used.
| 2) JOB_NAME="periodic-ci-ocp-helm-nightly" ;; | |
| 3) JOB_NAME="periodic-ci-ocp-operator-nightly" ;; | |
| 4) JOB_NAME="periodic-ci-ocp-helm-upgrade-nightly" ;; | |
| 5) JOB_NAME="periodic-ci-ocp-operator-auth-providers-nightly" ;; | |
| 2) JOB_NAME="periodic-ci-redhat-developer-rhdh-main-ocp-helm-nightly" ;; | |
| 3) JOB_NAME="periodic-ci-redhat-developer-rhdh-main-ocp-operator-nightly" ;; | |
| 4) JOB_NAME="periodic-ci-redhat-developer-rhdh-main-ocp-helm-upgrade-nightly" ;; | |
| 5) JOB_NAME="periodic-ci-redhat-developer-rhdh-main-ocp-operator-auth-providers-nightly" ;; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its release / branch independent. the main might confuse.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, we can keep it as it is
| @@ -0,0 +1,335 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally, I prefer to have the option to use flags to configure the options that I want. The current setup with a walkthrough works fine, and it's great for a newcomer, etc. The option to rerun the same config is great. But for me, flags are unbeatable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The flags now work great!
| @@ -0,0 +1,141 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We currently have linters for bash scripts only in .ibm folder, and basically all the bash scripts related to e2e and CI are there. It can make sense to have those scripts in e2e-tests folder, but it's kind of mixing up TypeScript with Bash now 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these are user-facing scripts that belong with the e2e-tests, not CI pipeline
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, but it would make sense to at least group them in a folder, maybe? So we can set up Prettier and ShellCheck (possibly in the future)
Co-authored-by: Zbyněk Drápela <61500440+zdrapela@users.noreply.github.com>
|
🚫 Image Push Skipped. The container image push was skipped because the build was skipped (either due to [skip-build] tag or no relevant changes with existing image) |
|
🚫 Image Push Skipped. The container image push was skipped because the build was skipped (either due to [skip-build] tag or no relevant changes with existing image) |
Add CLI flags (-j, -r, -t, -p, -s) to local-run.sh for automation and quick runs without interactive prompts. Also improve container-init.sh to pre-compute and save config before deployment so URLs are available even if deployment fails. Additional fixes: - Fix secrets parsing in local-test-setup.sh to handle special chars - Minor formatting fix in utils.sh for piped command Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
8b644ad to
82835ea
Compare
|
The image is available at: |
|
@subhashkhileri: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/review |
|
Persistent review updated to latest commit 82835ea |
zdrapela
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say this is ready to be used by RHDH devs. It works as expected with OCP
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: zdrapela The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| log::info "To run tests:" | ||
| echo " cd e2e-tests" | ||
| echo " yarn install" | ||
| echo " yarn playwright test --headed" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this can contain the --project=... with the specific project. Without the project specified, it will run all of them. Also the --headed can be explained (you often want to run it headlessly)
Extend local test runner to support non-OpenShift Kubernetes platforms: - Derive CONTAINER_PLATFORM from job name (*aks*, *eks*, *gke*, *osd*) - Add platform-specific cluster login (oc for OCP/OSD, kubectl for others) - Handle service account token creation for non-OpenShift clusters - Update container-init.sh to configure kubectl context for AKS/EKS/GKE - Add interactive menu options for AKS, EKS, GKE job selection - Update help text and examples for multi-platform usage Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
🚫 Image Push Skipped. The container image push was skipped because the build was skipped (either due to [skip-build] tag or no relevant changes with existing image) |
|



Description
https://issues.redhat.com/browse/RHIDP-11483
Which issue(s) does this PR fix
PR acceptance criteria
Please make sure that the following steps are complete:
How to test changes / Special notes to the reviewer